home *** CD-ROM | disk | FTP | other *** search
- For all "simple" configurations, the provided installer script should
- work OK. However, a little explanation might be needed:
-
- The SOCKS client needs to know when to (and when not to) attempt a network
- access via the SOCKS server. The reason it needs to do is that in typical
- networks behind a SOCKS proxy server, the "direct" network is accessed
- without the involvement of the proxy server. Only accesses outside that
- network need to go through the proxy. For example take the following
- network (the IP addresses are only examples; contact your network admin or
- provider for the correct addresses of your network):
-
-
- Your computer Other computers (that can be accessed without
- 192.0.2.46 going through the proxy server)
- _________ ______________
- / \ / \
- +-------+
- | |
- +---+---+ | .......... |
- | | |
- <----+------------+------+-------+-------------> network 192.0.2.0
- | netmask 255.255.255.0
- +---+---+ \
- | | | Proxy server
- +---+---+ / 192.0.2.1
- |
- |
-
- \___/
-
- The outside "world"
-
-
- In this case, you would give the following parameters to the installer:
-
- Address of the SOCKS proxy server: 192.0.2.1
- Network address of direct network: 192.0.2.0
- Netmask of direct network: 255.255.255.0
-
- Configured that way, all network accesses from your computer to the
- 192.0.2.[0-255] network would be direct accesses and anything outside
- that would be through the proxy server.
-
- The configuration is kept in ENVARC:socks.conf. For more details on
- complex configurations, please visit the "official" SOCKS site at:
-
- ftp://ftp.nec.com/pub/socks
-